SPR

Technote

Problem:
There are three possible workarounds to this issue:

Delete the record from the PNAB. This is not always a viable workaround
because the PNAB is sometimes used to store information not contained in the
Domino Directory or DirCat.

Enter the person's last name as lastname/hierarchy. This is also not always
viable since this can be cumbersome and not intuitive.

Create the document in the PNAB via the available action buttons in the Domino
Directory or mail file, but do not edit them. Again, not always a viable
solution for the same reason as stated in the first workaround.

This issue was reported to Lotus software Quality Engineering and was addressed
in Notes 5.0.3.

Excerpt from the Lotus Notes and Domino Release 5.0.3 MR fix list (available at
http://www.notes.net):

Templates - Personal NAB - Business Card

SPR# AUR4CKR3V - Fix Domino Directory template and Personal Address Book
template to allow fully qualified fullname in the contact form. [5.0.3]

Additional information:

This source of this problem appears to be that when manually creating a record
for a PNAB, the hierarchical information is not stored in the Person record.
If you create the record via the tools in your mail file, the hierarchical
information is retained. But, if you later edit that record, it is then
removed when the form recalculates. This causes the names to be similar, but
not the same; hence the Ambiguous Names dialog.

The source of this problem appears to be the following formula in the Fullname
field of the Person record:

@If(LastName = ""; @Return(FullName);"");
NewValue := @If(NameDisplayPref = "1"; FirstName + " " + LastName; LastName + "
" + FirstName);
NumElements := @Elements(FullName);
@If(NumElements <= 1; NewValue; NewValue:@Subset(FullName;-1*(NumElements-1))) More >